Systems and methods for detecting component rotation within a communication assembly

ABSTRACT

Systems and methods for detecting component rotation within a communication assembly are provided. In certain embodiments, a system includes a module; an adapter block that includes multiple front ports and multiple rear ports configured to receive an optical connector; a managing entity configured to control port identification for the front and rear ports; and a circuit board mounted to the adapter block, wherein the circuit board comprises multiple front contact assemblies and multiple rear contact assemblies, wherein each front port is associated with a front contact assembly and each rear port is associated with a rear contact assembly, wherein when a rear contact assembly is electrically coupled to a connector, the connector generates an event that is sent to the managing entity, whereupon the managing entity remaps the port identification for the front and rear ports.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 61/857,850, filed on Jul. 24, 2013, which is herebyincorporated herein by reference.

BACKGROUND

Telecommunications networks typically include numerous logicalcommunication links between various items of equipment. Often a singlelogical communication link is implemented using several pieces ofphysical communication media. For example, a logical communication linkbetween a computer and an inter-networking device such as a hub orrouter can be implemented as follows. A first cable connects thecomputer to a jack mounted in a wall. A second cable connects thewall-mounted jack to a port of a patch panel, and a third cable connectsthe inter-networking device to another port of a patch panel. A “patchcord or cable” cross connects the two together. In other words, a singlelogical communication link is often implemented using several segmentsof physical communication media.

Various types of physical layer management (PLM) systems can be used totrack connections made at patch panels and other types of equipment usedto make connections in communication networks. Generally, such PLMsystems include functionality to track what is connected to each port ofsuch equipment, trace connections that are made using such equipment,and provide visual indications to technicians at such equipment (forexample, by illuminating an LED that is associated with a patch panel ora port thereof).

One exemplary type of PLM system makes use of an Electrically ErasableProgrammable Read-Only Memory (EEPROM) or other storage device that isintegrated with or attached to a connector on a cable, fiber, or othersegment of communication media. The storage device is used to storeinformation about the connector or cable along with other information.The port (or other connector) into which the associated connector isinserted is configured to read the information stored in the EEPROM orother storage device when the connector is inserted at that port. Oneexample of such technology includes the QUAREO family of products thatare commercially available from TE Connectivity.

Another type of PLM system makes use of so-called “ninth wire”technology. Ninth wire technology makes use of special cables thatinclude an extra conductor or signal path (also referred to here as the“ninth wire” conductor or signal path) that is used for determiningwhich port each end of the cables is inserted into. Ninth wiretechnology can be used with various types of cables, such as,twisted-pair copper cables and optical cables (in the latter case usinghybrid optical cables that include one or more copper wires that serveas the ninth wire). One example of ninth wire technology includes theAMPTRAC family of products that are commercially available from TEConnectivity.

Another type of PLM system makes use of radio frequency identification(RFID) tags and readers. With this type of RFID PLM system, an RFID tagis attached to or integrated with a connector on a cable, fiber, orother segment of communication media. The RFID tag is used to storeinformation about the connector or segment of communication media alongwith other information. The RFID tag can be read after the associatedconnector is inserted into a corresponding jack or other port using anRFID reader.

PLM systems typically include management software that aggregates thecaptured information and stores it in one or more databases. One exampleof such management software is the Infrastructure Configuration Manager(ICM) software that is commercially available from TE Connectivity.

In addition to information about the connections and cabling used tomake them, these databases also typically store information about theother equipment used to make the connections. Examples of such equipmentinclude patch panels, distribution frames, and active networking devicessuch as switches, routers, and gateways. Examples of information that isstored in the database about such equipment include information aboutthe make and model of the equipment and where it is installed in thenetwork.

Typically, information about where such equipment is installed in thenetwork must be manually entered. This is commonly the case even for“intelligent” equipment that can be automatically discovered by the PLMmanagement software and queried for its identification information (forexample, serial number and make and model).

For example, in one common usage scenario, a frame is installed in anequipment room or data center of an enterprise or in a central office ofa telecommunication service provider. The frame is designed to housemultiple sub-assemblies that are used to make connections betweencables. One example of such a frame is an optical distribution frame(ODF) into which multiple chassis can be inserted. In this example, eachchassis is designed to hold multiple adapter packs on one or more traysthat slide in and out of the chassis. Each adapter pack comprisesmultiple optical adapters, where each of the optical adapters isconfigured to optically connect an optical cable terminated with anoptical connector (such as an LC or SC connector) with another opticalcable terminated with a corresponding optical connector.

Each optical adapter in each adapter pack can be designated as a port inthe adapter pack. When an adapter pack is installed in a chassis, thereis a chance that the adapter pack may be installed in a reversedposition because, in certain applications, one side of an adapter packthat connects to optical connectors may be indistinguishable from anopposite side that likewise connects to optical connectors. When anadapter pack is in a reversed position, the management software mayincorrectly identify the different ports in the adapter pack.

As noted above, even when the frame includes some type of PLMintelligence that enables the frame to be discovered by PLM managementsoftware and queried for identification information associated with thatframe (for example, a serial or other identification number and a makeand model), location information for that frame typically must bemanually entered into the PLM management system (for example, using aWeb interface or mobile application). This is because the frame istypically not aware of where it is located. The PLM management system isthen able to associate the manually entered location information withthe identification information that the PLM management software was ableto automatically discover.

Also, whenever a sub-assembly (for example, an optical chassis of thetype noted above) is installed in the frame, location information forthat sub-assembly must also be manually entered into the PLM managementsystem. The location information for each sub-assembly includes wherethat sub-assembly is located (for example, a physical location and/orwhich frame the sub-assembly has been inserted into) as well as whichslot or position within the frame into which the sub-assembly has beeninserted.

The location information for each such sub-assembly typically must bemanually entered even if the sub-assembly otherwise includes PLMintelligence that enables the sub-assembly to be discovered and queriedby the PLM management software for its identification information. Thisis because the sub-assembly typically is not aware of where it islocated. The need to manually enter location information for thesub-assembly adds an additional manual step to the work-flow associatedwith installing the sub-assembly, which increases the time required tocomplete the work flow and which can result in incorrect data beingmanually entered. Moreover, it is common that when a frame is initiallydeployed, less than the maximum number of sub-assemblies that could behoused in that frame are actually installed in the frame during theinitial deployment. As a result, location information for the varioussub-assemblies in a given frame might be manually entered by differentpeople at different times.

DRAWINGS

Understanding that the drawings depict only exemplary embodiments andare not therefore to be considered limiting in scope, the exemplaryembodiments will be described with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 is a block diagram of an exemplary embodiment of a communicationsystem;

FIG. 2 is a flow diagram of an exemplary embodiment of a method ofautomatically associating location information with a sub-assemblyinstalled in a frame;

FIG. 3 is a block diagram of an exemplary embodiment of an adapterblock; and

FIG. 4 is a flow diagram of an exemplary embodiment of a method fordetecting module rotation within a communication sub-assembly.

In accordance with common practice, the various described features arenot drawn to scale but are drawn to emphasize specific features relevantto the exemplary embodiments.

DETAILED DESCRIPTION

FIG. 1 shows one exemplary embodiment of a system that can be used toautomatically associate location information with communicationsub-assemblies 130-133 that are inserted into a larger communicationassembly 106. The larger communication assembly 106 into which thecommunication sub-assemblies 130-133 can be inserted is configured tophysically hold the sub-assemblies 130-133 in place. The assembly 106includes a plurality of slots or positions and each of thesub-assemblies 130-133 is inserted into one of the positions in theassembly 106. Each sub-assembly 130-133 is used to make connectionsbetween various cables (such as fiber optic cables terminated with LC,SC, Multiple-Push-On (MPO) connectors or copper cables such as CAT-5 orCAT-6 twisted-pair cables terminated with RJ-45 connectors).

In the exemplary embodiment described here in connection with FIG. 1,the assembly 106 comprises an optical distribution frame 106 (alsoreferred to here as the “optical distribution frame” 106 or simply the“frame” 106). Also, in this exemplary embodiment, the sub-assemblies130-133 comprise chassis 130-133 that are configured to hold multiplefiber optic modules 150-153 (for example, in a 4 Rack Unit (RU) sizedchassis). The sub-assemblies 130-133 are also referred to here as the“chassis” 130-133. The optical distribution frame 106 comprises a framestructure 107 that is configured to have a plurality of positions, wherea chassis 130-133 can be inserted into each of the positions. For easeof explanation, the frame 106 is shown in FIG. 1 as being configured tohouse up to four chassis 130-133, and each chassis 130-133 is shown asbeing configured to house up to two fiber optic modules 150-153;however, it is to be understood that the frame 106 can be configured tohouse any number of chassis 130-133, and each chassis 130-133 can beconfigured to house any number of fiber optic modules 150-153.

Each optical module 150-153 is implemented as an optical tray that isconfigured to hold at least one multiple adapter pack 170-173. Eachadapter pack 170-173 comprises multiple optical adapters 180-183, whereeach of the optical adapters 180-183 is configured to optically connectan optical cable (not shown) terminated with an optical connector (suchas an LC, SC, or a Multi-fiber Push On (MPO) connector) with anotheroptical cable (not shown) terminated with a corresponding opticalconnector. Again, for ease of explanation, in FIG. 1, each module150-153 is shown as holding two adapter packs 170-173, and each adapterpack 170-173 is shown in FIG. 1 as holding up to two adapters 181;however, it is to be understood that each module 150-153 can beconfigured to hold any number of adapter packs 170-173, and each adapterpack 170-173 can be configured to hold any number of optical adapters180-183. Also, it is to be understood that the techniques described herecan be used for other types of connection devices including, forexample, ones where a single cable (or a single cable bundle) is brokenout in order to be connected to multiple cables or cable bundles (suchas, for example, MPO, splitter, or cassette type devices).

In the exemplary embodiment described herein connection with FIG. 1,each of the connectors includes a respective non-volatile storage device(such as an EEPROM) that is used to gather information about theconnector or the cable (for example, identification information for thecable or connector such as serial number or other identifier and makeand model). Each module 150-153 includes a respective module controller160-163. Each module 150-153 and the corresponding adapter packs 170-173and optical adapters 180-183 are configured so that the modulecontroller 160-163 for that module 150-153 can determine whether aconnector is inserted into each optical adapter 180-183 and read thestorage device associated with that inserted connector (if there isone). For example, each optical adapter 180-183 includes one or morecontacts or terminals that come into electrical contact withcorresponding contacts or terminals on any connector that is insertedinto the adapter 180-183, where such contacts or terminals are used toelectrically couple the storage device for that connector to thecorresponding module controller 160-163 so that the module controller160-163 can determine if a connector is inserted into each opticaladapter 180-183 and read information from a storage device attached tosuch a connector (if any). In some applications, the data read from thestorage device is used to track connections made at the frame 106. Insome applications, connectors that include such storage devices are notused and, instead, connections are tracked by inferring connectionsusing the functionality that determines whether a connector is insertedin each adapter or port. In some applications, a combination of theforegoing approaches is used.

Examples of such chassis 130-133, modules 150-153, adapter packs170-173, and optical adapters 180-183 are described in the followingUnited States Provisional Patent Applications: U.S. Provisional PatentApplication Ser. No. 61/761,048, filed on Feb. 5, 2013, titled “OpticalAssemblies with Managed Connectivity”; U.S. Provisional PatentApplication Ser. No. 61/761,034, filed on Feb. 5, 2013, titled “OpticalAssemblies with Managed Connectivity”; U.S. Provisional PatentApplication Ser. No. 61/761,042, filed on Feb. 5, 2013, titled “OpticalAssemblies with Managed Connectivity”; U.S. Provisional PatentApplication Ser. No. 61/761,009, filed on Feb. 5, 2013, titled “SlidableTelecommunications Tray with Cable Slack Management”; and U.S.Provisional Patent Application Ser. No. 61/763,347, filed on Feb. 11,2013, titled “Slidable Telecommunications Tray with Cable SlackManagement”. All of the preceding applications are incorporated hereinby reference.

Each of the adapter packs 170-173 contains multiple adapters also knownas ports. For example, an adapter pack, such as adapter pack 170, mayhave 24 ports divided between two opposing sides of the adapter pack170. The adapter pack 170 provides connectivity between opticalconnectors that may have LC, SC, Multiple-Push-On (MPO) type connectors.In certain implementations, for example, when the adapter pack 170provides an LC/LC connection, an SC/SC connection, an LC/SC connection,an MPO/MPO connection, or the like, the opposite sides of the adapterpack 170 may appear identical. Due to the same appearance of theopposite sides of the adapter pack 170, a user may install the adapterpack 170 in a normal position and a reversed position.

To determine whether an adapter pack 170 is installed in a normalposition or a reversed position, each port in the adapter pack 170includes at least one general purpose input/output (GPIO) pin. Onopposing sides of the adapter pack 170, the GPIO pins in the ports aretied to different voltage levels, such that the connectors can determinewhich side of the adapter pack is connected to the adapters. Forexample, on one side of the adapter pack 170, the GPIO pins are tied toa relatively high voltage level, while on the opposite side of theadapter pack 170, the GPIO pins are tied to a low voltage. When aconnector connects to a port in the adapter pack 170, the connector usesthe voltage level of the GPIO pin to determine if the adapter pack 170is in a normal position or reversed position.

In at least one exemplary implementation, when the adapter pack 170 isin a normal position, the connector is connected to a port in theadapter pack 170 where the GPIO pin is providing a high voltage level.As the adapter pack 170 is in the normal position, the connectorconnects to the port in the adapter pack 170 and functions according tonormal operations. In contrast, when the adapter pack 170 is in areversed position, the connector connects to a port in the adapter pack170 where the GPIO pin is providing a low voltage level. Because theGPIO pin is providing a low voltage, the connector notifies a managemententity 102. For example, a connector generates an event that istransmitted to the management entity 102. Where the management entity102 reverses the port numbering of the different ports in the adapterpack 170. Further, the GPIO pin can be part of adapter packs 170-173 inthe frame structure 107.

In a further exemplary implementation, a module 150 may be installed inthe chassis in either a normal position or a reverse position. Like theadapter packs 170-173, a module 150 may include a GPIO pin thatindicates whether a module is installed in the normal or reverseposition. When the module 150 is installed in a normal position, thereare no events generated through the module GPIO pin that arecommunicated to the management entity 102. However, when the module isinstalled in a reverse position, the module GPIO pin raises a moduleevent that is communicated to the management entity 102. Upon receivinga module event indicating that a module 150 is installed in a reverseposition, the management entity 102 may indicate that the module 150 isin a reverse position to a user or an administrator of the frame 106.However, in at least one exemplary implementation in contrast to theadapter packs 170-173, the management entity 102 does not remap portswhen a module is installed in the reverse position.

In the exemplary embodiment shown in FIG. 1, each chassis 130-133includes a respective master controller 140-143 that is electricallycoupled to the module controller 160-163 for each module 150-153 that isincluded in that chassis 130-133 (for example, using a respective flexcircuit interconnect). In this exemplary embodiment, the mastercontroller 140-143 and its associated module controllers 160-163 areconfigured to use a master-slave scheme for communicating with oneanother. In such a scheme, the master controller 140-143 serves as the“master,” and each of the module controllers 160-163 serves as a“slave.” For example, in one implementation of such a scheme, eachmodule controller 160-163 determines when a connector has been insertedinto an optical adapter 180-183 associated with that module controller160-163 and reads information from the storage device attached orotherwise associated with that connector. When prompted to do so by theassociated master controller 140-143, each module controller 160-163informs the master controller 140-143 of any state changes for any ofthe optical adapters 180-183 associated with that module controller160-163 (for example, that a connector has been inserted or removed froman optical adapter 180-183) and forwards to the master controller140-143 information read from storage devices inserted into opticaladapters 180-183 associated with that module controller 140-143.

In the exemplary embodiment shown in FIG. 1, each chassis 130-133includes an at least one management network interface 190-193 that canbe used to couple the master controller 140-143 to an IP network 110that is used for communicating the PLM information described below to amanagement entity 102. In an example implementation of such anembodiment, the management network interface 190-193 for each chassis130-133 is implemented using an ETHERNET network interface (andassociated RJ-45 port) so that the corresponding master controller140-143 can be coupled to the IP network 110 using a CAT-5 or CAT-6twisted-pair copper cable. It is to be understood, however, that themanagement network interface 190-193 can be implemented in other ways.

It is noted that, for ease of explanation, the IP network 110 is shownusing a separate cloud symbol, but it is to be understood that the frame106, chassis 130-133, and cabling described here can be used toimplement a part of the IP network 110 over which the PLM information iscommunicated. Alternatively, the IP network 110 over which the PLMinformation is communicated can be kept separate from the network thatthe frame 106, chassis 130-133, and cabling are a part of.

The management entity 102 is typically implemented as software that runson a computer that is coupled to the IP network 110. The managemententity 102 is configured to receive information pertaining to variousdevices and media used to implement the physical layer in the network(including, but not limited to, the chassis 130-133 and frame 106 andthe cables and connectors that make connections there). The physicallayer information (PLI) that is communicated to the management entity102 includes information about various devices in the network (alsoreferred to here as “device information”) as well as information aboutany segments of physical communication media attached to the ports ofthose devices (also referred to here as “media information”). The deviceinformation includes, for example, an identifier for each device, a typeidentifier that identifies the device's type, and port information thatincludes information about the device's ports. The media informationincludes information that is read from storage devices that are attachedto various segments of physical communication media.

Examples of media information that can be stored in such storage devicesinclude, without limitation, an identifier that uniquely identifies thatparticular segment of physical communication media (similar to anETHERNET Media Access Control (MAC) address but associated with thephysical communication media and/or connector attached to the physicalcommunication media), a part number, a plug or other connector type, acable or fiber type and length, a serial number, a cable polarity, adate of manufacture, a manufacturing lot number, information about oneor more visual attributes of physical communication media or a connectorattached to the physical communication media (such as information aboutthe color or shape of the physical communication media or connector oran image of the physical communication media or connector), and otherinformation used by an Enterprise Resource Planning (ERP) system orinventory control system. In other embodiments, alternate or additionaldata is stored in such storage devices. For example, testing, mediaquality, or performance information can be stored in such storagedevices. The testing, media quality, or performance information, forexample, can be the results of testing that is performed when aparticular segment of media is manufactured or installed.

The information provided to the management entity 102 can also includeinformation that is manually entered (for example, using a Web interfacethat is implemented by the management entity 102 or a mobileapplication).

The management entity 102 includes or uses a database or other datastore (not shown) for storing the information provided to it. Themanagement entity 102 also includes functionality that provides aninterface for external devices or entities to access the physical layerinformation maintained by the management entity 102. This access caninclude retrieving information from the management entity 102 as well assupplying information to the management entity 102. In this example, themanagement entity 102 is implemented as “middleware” that is able toprovide such external devices and entities with transparent andconvenient access to the information maintained by the management entity102. Because the management entity 102 aggregates information from therelevant devices in the network and provides external devices andentities with access to such information, the external devices andentities do not need to individually interact with all of the devices inthe network that provide information to the management entity 102, nordo such devices need to have the capacity to respond to requests fromsuch external devices and entities.

The management entity 102, in this example, implements an applicationprogramming interface (API) by which application-layer functionality cangain access to the physical layer information maintained by themanagement entity 102 using a software development kit (SDK) thatdescribes and documents the API.

More information about physical layer information and the aggregationpoint 152 can be found in U.S. Provisional Patent Application Ser. No.61/152,624, filed on Feb. 13, 2009, titled “MANAGED CONNECTIVITY SYSTEMSAND METHODS” and U.S. patent application Ser. No. 12/705,497, filed onFeb. 12, 2010, titled “AGGREGATION OF PHYSICAL LAYER INFORMATION RELATEDTO A NETWORK”, both of which are hereby incorporated herein byreference.

In the exemplary embodiment shown in FIG. 1, the master controller140-143 in each chassis 130-133 is configured to interact with, monitor,and/or control the operation of the components of the chassis 130-133(for example, any buttons (or other input components) and any lightemitting diodes (LEDs) (or other visual indicators) incorporated intothe body of the chassis 130-133 itself) as well as the modulecontrollers 180-183. Also, the master controller 140-143 in each chassis130-133 is configured to interact with external entities via the IPnetwork 110. For example, each master controller 140-143 is configuredto implement appropriate functionality and protocols for the mastercontroller 140-143 to obtain an IP address (for example, a static IPaddress that is manually assigned to the master controller 140-143 via aWeb or mobile app interface that is implemented by the master controller140-143 or a dynamic IP address that is assigned to the modulecontroller 140-143 via a Dynamic Host control Protocol (DHCP) server forthe IP network 110). Also, each master controller 140-143 is configuredto implement appropriate functionality and protocols for the mastercontroller 140-143 to be discovered by, and to discover, the managemententity 102. This discovery of and by the managing entity 102 can be donemanually (for example, by manually providing an address for the mastercontroller 140-143 to the managing entity 102 and by manually providingan address for the managing entity 102 to the master controller 140-143using, for example, a Web or mobile app interface implemented by themaster controller 140-143 and the managing entity 102) or automatically(for example, using a suitable discovery protocol such as the UniversalPlug and Play (UPnP) discovery protocol).

In the exemplary embodiment shown in FIG. 1, the frame 106 includes aframe controller unit 108 that is attached to the structure thatimplements the frame. For example, in one implement of such embodiment,the frame controller unit 108 is attached to the top of such structure.In other implementations, the frame controller unit 108 is locatedelsewhere in the frame 106 (for example, on the bottom of the framestructure).

In this embodiment, the frame controller unit 108 includes a framecontroller 118 and an ETHERNET switch 119. The frame controller 118 isconfigured to interact with, monitor, and/or control the operation ofthe components of the frame controller unit 108 (for example, theETHERNET switch 119 as well as any buttons (or other input components)and any light emitting diodes (LEDs) (or other visual indicators)incorporated into the frame controller unit 108) and the frame 106 (forexample, any LEDs that are mounted to the frame 106 itself). Also, theframe controller 118 is configured to interact with external entitiesvia the IP network 110. For example, the frame controller 118 isconfigured to implement appropriate functionality and protocols for theframe controller 118 to obtain an IP address (for example, a static IPaddress that is manually assigned to the frame controller 118 via a Webor mobile app interface that is implemented by the frame controller 118or a dynamic IP address that is assigned to the frame controller 118 viaa DHCP server for the IP network 110). Also, the frame controller 118 isconfigured to implement appropriate functionality and protocols for theframe controller 118 to be discovered by, and to discover, themanagement entity 102. This discovery of and by the managing entity 102can be done manually (for example, by manually providing an address forthe frame controller 118 to the managing entity 102 and by manuallyproviding an address for the managing entity 102 to the frame controller118 using, for example, a Web or mobile app interface implemented by theframe controller and managing entity 102) or automatically (for example,using a suitable discovery protocol such as the UPnP discoveryprotocol).

The ETHERNET switch 119 includes two sets of ports 115 and 117. One setof ports 115 are standard ETHERNET ports in which ETHERNET cables can beeasily inserted and removed in connection with the normal operation ofthe frame 106. These ports 115 are also referred to here as “standardports” 115. In the exemplary embodiment shown in FIG. 1, the ETHERNETswitch 119 includes two standard ports 115, one of which is used toconnect the ETHERNET switch 119 (and the other devices coupled to theother ports 115 and 117 of the switch 119) to the IP network 110. Thisstandard port 115 is also referred to here as the “upstream port” 115.The other standard port 115 is an auxiliary port 115 that can be used,for example, to couple a wireless access point 112 to the IP network 102or to daisy chain two or more frames 106 (and their associated framecontrollers 118) together (for example, as described further in moredetail below).

The ETHERNET switch 119 also includes a second set of ports 117 that areconfigured so that the ETHERNET cables inserted into those ports 117cannot be easily removed from the ports 117 in connection with thenormal operation of the frame 106. In the following description, theseports 117 are also referred to here as the “fixed ports” 117. This canbe done using a suitable connector or attachment mechanism.

For each of the fixed ports 117, an ETHERNET cable 120-123 is insertedinto that fixed port 117 that is configured to be inserted into themanagement network interface 190-193 of a chassis 130-133 that isinserted at one particular position in the frame 106 and is configuredso that the cable 120-123 cannot be inserted into the management networkinterface 190-193 of a chassis 130-133 inserted into any of the otherpositions in the frame 106. This can be done, for example, by routingand attaching each ETHERNET cable 120-123 to the frame 106 so that thereis only enough slack at the chassis end of that ETHERNET cable 120-123to be able to physically reach the management network interface 190-193of a chassis 130-133 inserted into only one predetermined chassisposition in the frame 106 and not be able to physically reach themanagement network interfaces 190-193 of chassis 130-133 inserted intothe other chassis positions in the frame 106.

In this way, a relationship between each of the fixed ports 117 and aparticular chassis position in the frame 106 is maintained. Thisrelationship can be used to associate any chassis 130-133 that isdirectly coupled to that fixed port 117 with that particular chassisposition in that particular frame 106. This relationship can be used toautomatically associate location information with a chassis 130-133inserted into the frame 106. This location information for the chassis130-133 includes, for example, the location of the frame 106 and thechassis position within the frame 106 that the chassis 130-133 isinserted into. The management entity 102 can do this. Also, this can bedone by the frame controller 118.

The frame controller 118 is communicatively coupled to the ETHERNETswitch 119 so that it is able to communicate with the managing entity102 via the IP network 110. Also, as is described in more detail below,the frame controller 118 is configured to retrieve from the ETHERNETswitch 119 information that maps each of the ports 115 and 117 of theswitch 119 to MAC addresses that can be accessed via that switch port(for example, by retrieving the port map table that is maintained by anautomatic translation unit (ATU) or lookup engine in the ETHERNET switch119).

In exemplary embodiment shown in FIG. 1, power can be supplied to theactive components of the chassis 130-133 (and the modules 150-153included therein) using Power over Ethernet (POE). In this embodiment,the ETHERNET switch 119 is configured to source POE power over the ports115 and the 117 and is coupled to a 48 Volt Direct Current (DC) powersource 114 in order to do so. This 48V DC power can also be used topower the active components of the frame 106 (including the framecontroller unit 108 and any LEDs attached to the frame 106). It is to beunderstood, however, that power can be supplied in other ways.

The auxiliary port 115 can also be used to connect multiple frames 106(and the associated frame controller units 108) in a daisy-chainconfiguration. In such a configuration, the upstream port 115 for afirst frame 106 is connected directly to the IP network 110 (that is, isnot connected to the IP network 110 through another one of the frames106). The upstream port 115 of a second one of the frames 106 isconnected to the auxiliary port 115 of the first frame 106, the upstreamport 115 of a third one of the frames 106 is connected to the auxiliaryport 115 of the second frame 106, and so on. The auxiliary port 115 ofthe last frame 106 in the daisy chain is not used for implementing thedaisy chain and can be used for other purposes (for example, forconnecting a wireless access point 115 to the IP network 110). Thetechniques for automatically associating location information withchassis 130-133 inserted into a frame 106 can be used with such adaisy-chain configuration.

FIG. 2 is a flow diagram of one exemplary embodiment of a method 200 ofassociating location information with a communication sub-assembly (suchas a chassis) that is inserted into a frame (or similar assembly intowhich multiple communication sub-assemblies can be inserted). Theexemplary embodiment shown in FIG. 2 is described here as beingimplemented using the system shown in FIG. 1, though it is to beunderstood that other embodiments can be implemented in other ways.

Method 200 comprises communicatively coupling the frame controller 118in the frame 106 to management entity 102 (block 202). In one commonusage scenario, the frame 106 is installed in an equipment room or datacenter of an enterprise or in a central office of a telecommunicationservice provider. In this example, the frame controller 118 is connectedto the IP network 110 by connecting one of the standard ports 115 of theETHERNET switch 119 included in the frame controller unit 108 to the IPnetwork 110 using an appropriate cable (for example, a CAT-5 or CAT-6cable). Then, as described above, the frame controller 118 obtains an IPaddress (either manually or automatically using, for example, DHCP) anddiscovers, and is discovered by, the management entity 102 (again,either manually or automatically using UPnP).

Method 200 further comprises automatically providing identificationinformation for the frame 106 to the management entity 102 (block 204).In this example, the management entity 102 automatically obtainsidentification information for the frame 106 (for example, a serialnumber and/or another identifier assigned to the frame 106 and/or makeand model information for the frame 106) by using the IP network 110 toquery the frame controller 118 for such information. Although theidentification information is described here as being providedautomatically to the management entity 102, it is to be understood thatsuch information could be provided manually. Also, as a part of theinformation that is provided to the management entity 102, informationthat identifies which of the fixed ports 117 is associated with whichchassis position in the frame 106 is also to be provided to themanagement entity 102.

Method 200 further comprises providing location information for theframe 106 to the management entity 102 (block 206). In this example,location information for the frame 106 is manually entered and providedto the management entity 102 (for example, using a Web or mobile appinterface implemented by the management entity 102). This locationinformation can include, for example, information that specifies aphysical location for the frame 106 (for example, GPS coordinates, anaddress for the building in which the frame 106 is installed, and/or anumber or other identifier for the floor, room, and/or row where theframe 106 is installed). This location information can be specified inany suitable away (for example, using absolute and/or relativecoordinates or addresses).

Method 200 further comprises, when a chassis 130-133 is installed in theframe 106 in one of the chassis positions (block 208), connecting themanagement network interface 190-193 of that chassis 130-133 to thepredetermined fixed port 117 of the ETHERNET switch 119 that isassociated with that chassis position (block 210). In this example, themaster controller 140-143 obtains an IP address (either manually orautomatically using, for example, DHCP) and discovers, and is discoveredby, the management entity 102 (again, either manually or automaticallyusing UPnP). When a chassis 130-133 is not installed in the frame (block208), the master controller 140-143 waits for a chassis 130-133 to beinstalled in the frame.

Method 200 further comprises automatically providing identificationinformation for the chassis 130-133 to the management entity 102 (block212) in connection with the chassis 130-133 being inserted into theframe 106. In this example, the management entity 102 automaticallyobtains identification information for the chassis 130-133 (for example,a serial number and/or other identifier assigned to the chassis 130-133and module 150-153, adapter packs 170-173, and adapters 180-183 housedwithin the chassis 130-133, and any connectors or cables attachedthereto, and/or make and model information for any of the foregoing) byusing the IP network 110 to query the master controller 140-143 for thatchassis 130-133 for such information. Also, in this example, a mediaaccess control (MAC) address associated with the management networkinterface 190-193 is also communicated to the management entity 102.

Method 200 further comprises automatically providing MAC-address-to-portmapping information from the frame controller 118 to the managemententity 102 (block 214). In this example, the frame controller 118 readsthe routing tables maintained by the ATU or lookup engine in the switch119 in order come up with the MAC-address-to-port mapping information.This MAC-address-to-port mapping information is provided to themanagement entity 102 via the IP network 110.

Method 200 further comprises automatically associating locationinformation with the chassis 130-133 that has just been inserted into achassis position in the frame 106 (block 216). In this example, themanagement entity 102 does this by using the MAC address for themanagement network interface 190-193 of that chassis 130-133 todetermine which frame 106—and which chassis position within that frame106—the chassis 130-133 is inserted into. The frame 106 that the chassis130-133 is inserted into is the one whose MAC-address-to-port mappinginformation includes the MAC address for the management networkinterface 190-193. Then, the management entity 102 associates thelocation information for that frame 106 (which was manually entered inconnection with block 206) with that chassis 130-133 (and module150-153, adapter packs 170-173, and adapters 180-183 in that chassis130-133 and any connectors or cables attached thereto). Also, themanagement entity 102 determines the chassis position within that frame106 by using MAC address for the management network interface 190-193 ofthat chassis 1301-133 and the MAC-address-to-port mapping information todetermine which fixed port 117 that chassis 130-133 is connected to.

In this way, location information can be associated with the chassis130-133 automatically (that is, without having to manually enter suchlocation information). This eliminates the manual data entry step thatwould otherwise be needed each time a chassis 130-133 is inserted intothe frame 106 and the need for such information to be manually enteredby different people at different times, when the frame 106 is initiallydeployed with less than all of the chassis positions filled with chassis130-133.

FIG. 3 is a diagram illustrating an adapter pack assembly 300 havingports on opposing sides. In certain implementations, the adapter packassembly 300 functions as one of adapter packs 170-173 in FIG. 1. Theadapter block assembly 300 has front ports 301 and rear ports 302. Frontports 301 may receive optical connectors (e.g., optical connectors 350)when the adapter block assembly 300 is in a normal position.Alternatively, the rear ports 302 may receive the optical connectorswhen the adapter block assembly 300 is in a reversed position.

In at least one implementation, the adapter block assembly 300 includesa first adapter block 310A, a second adapter block 310B, a joiningmember 320, and a circuit board 330. The joining member 320 physicallycouples the first and second adapter blocks 310A, 310B together. Thecircuit board 330 couples to the joined first and second adapter blocks310A, 310B. Contact assemblies 360 and circuit board components 334(e.g., memory) are mounted to the circuit board 330. The contactassemblies 360 face towards the adapter blocks 310A, 310B. The cover 340extends over at least some of the components 334 of the circuit board330.

In a further example, a contact assembly 360 is disposed between theadapter block 310 and the circuit board 330. A front contact assembly360 corresponds with the front ports 301 and a rear contact assembly 360corresponds with the rear ports 212. Contacts of the contact assembly360 extend through apertures 315 in the adapter block 310. The contactsare positioned and oriented so that the contact sections align with thecontact region 352 of optical connectors 350 received at correspondingports 301 and 302. In at least one implementation, the contact assembly360 includes a GPIO for each of the front ports 301 and rear ports 302.In certain implementations, the GPIOs associated with the front ports301 are tied to a high voltage and the GPIOs associated with the rearports 302 are tied to a low voltage. When, the connector 350 is insertedinto a front port 301, the contact region 352 of the connector 350 comesinto contact with the GPIO pin in the contact assembly 360 that isassociated with a front port 301. When the connectors 350 are connectedto front ports 301, the assembly block 300 is in a normal position.However, the assembly block 300 may be placed within a frame assembly ina reversed position, such that the connectors 350 are connected to rearports 302. When the connector 350 is inserted into a rear port 302, thecontact region 352 of the connector 350 comes into contact with a GPIOpin in the contact assembly 360 that is associated with a rear port 302.When the connectors 350 are connected to rear ports 302, the assemblyblock 300 is in a reversed position, and the connector 350 generates anevent that is communicated to a managing entity of the frame assemblythat contains the adapter block assembly 300.

In certain exemplary embodiments, when the managing entity receives anevent from the connector 350, the managing entity reverses the numbersassigned to the different ports. For example, in an adapter block 310having 24 ports, a connector 350 connected into the first front portwill cause the managing entity to identify the port as port 1 andincrementally assign numbers to the rest of the ports. However if theadapter block 310 is installed in a reverse position, the first portwould be port 24 if the adapter block 310 were in the normal position.As described above, when the connector 350 is connected to the firstrear port, the connector 350 sends an event to the managing entity thatcauses the managing entity to reassign the numbers that identify theports. When there are 24 ports, the managing entity re-assigns port 1 toport 13, port 2 to port 14, port 3 to port 15, port 13 to port 1, port14 to port 2, and so forth. Thus, the adapter block 310 may be installedin either the normal position or the reverse position without affectingthe identification of the ports. As shown here, the adapter block mayinclude different configurations. For example, the terms “rear” and“front” are merely intended to differentiate the location of the portson the adapter block assembly.

FIG. 4 is a flow diagram of one exemplary embodiment of a method 400 ofdetecting component rotation within a communication sub-assembly (suchas a chassis) that is inserted into a frame (or similar assembly intowhich multiple communication sub-assemblies can be inserted). Theexemplary embodiment shown in FIG. 4 is described here as beingimplemented using the system shown in FIG. 1 and the adapter block 300shown in FIG. 3, though it is to be understood that other embodimentscan be implemented in other ways.

Method 400 comprises placing a module 150 within a chassis 130 (block402). In one common usage scenario, the module 150 may be a slidabletray that is placed within the chassis 130. In certain implementations,it may be difficult for a user to differentiate the front side of themodule 150 from the rear side of the module 150 as the two opposingsides of the module 150 may appear identical. Due to the difficulty indifferentiating the different sides of the module 150, the module 150may be installed in either a reverse position or a normal positionwithin the chassis 130.

Method 400 also comprises determining if a module event is generated(block 404). In this example, the module 150 may include a GPIO pin.When the module 150 is installed in the reverse position, the GPIO pinmay make contact in such a way that a signal is transmitted to themanaging entity, where the managing entity interprets the reception ofthe signal as a generated module event. When the module 150 is installedin the normal position, no signal is generated or transmitted to themanaging entity. In at least one exemplary implementation, method 400includes notifying the user of the position of the module 150, when amodule event is generated (block 406).

Further, method 400 comprises placing an adapter block 300 within themodule 150 (block 408). In one common usage scenario, an adapter block300 is placed within a module 150 located within the chassis 130. Incertain implementations, it is difficult for a user to differentiate thefront side of an adapter block from the rear side of an adapter block asthe two opposing sides of the adapter block may appear and functionsubstantially identical. Due to the difficulty in differentiating thedifferent sides of the adapter block, the adapter block may be installedin either a reverse orientation or a normal orientation.

Method 400 further comprises coupling a connector 350 to a port in theadapter block (block 410). In this example, an optical connector 350 isconnected to one of the ports in the adapter block 300. When the adapterblock 300 is in the normal position, the connector 350 is connected toone of the front ports 301. In contrast, when the adapter block 300 isin the reverse position, the connector 350 is connected to one of therear ports 302. In certain implementations, to correctly routeinformation through the correct connector, a managing entity accuratelyidentifies to which port the connector 350 is connected. However, if theadapter block 300 is installed in a reverse position, the port mappingswill be incorrect

Method 400 further comprises determining if an adapter event isgenerated (block 412). In this example, the ports on the adapter block300 each include a GPIO pin. In the front ports 301, the GPIO pins maybe tied to a logically high voltage. In contrast, in the rear ports 302,the GPIO pins may be tied to a logically low voltage. When the connector350 is connected into a front port 301, the connector 350 connects to aGPIO pin that is tied to logical high and does not generate an event.However, when the connector 350 is connected into a rear port 302, theconnector 350 connects to a GPIO pin that is tied to logical low andgenerates an event. The connector 350 then transmits the generated eventto a managing entity over the chassis.

When an event is generated, method 400 further comprises remappingidentification of the port (block 416). When a managing entity receivesan event due to the adapter block 300 being installed in a reverseposition, the managing entity remaps the identification for the frontports 301 and rear ports 302. In at least one example, where there are12 front ports and 12 rear ports, ports 1-12 are front ports 301 andports 13-24 are rear ports 302. When the managing entity receives thegenerated event, the managing entity remaps the ports such that ports1-12 are rear ports 302 and ports 13-24 are front ports 301. Thus, afterremapping the ports, the managing entity is able to identify thelocation of the ports within the chassis 130. When no event is generated(block 412), method 400 comprises maintaining the identification of theport (block 414). Thus, the managing entity remaps the ports upon thereception of an event, when no event is received, the managing entitymaintains the original port identification.

EXAMPLE EMBODIMENTS

Example 1 includes a system for detecting component rotation, the systemcomprising: a module; an adapter block installed in the module, theadapter block comprising a plurality of front ports and a plurality ofrear ports configured to receive an optical connector; a managing entityconfigured to control port identification for the plurality of frontports and the plurality of rear ports; and a circuit board mounted tothe adapter block, wherein the circuit board comprises a plurality offront contact assemblies and a plurality of rear contact assemblies,wherein each front port in the plurality of front ports is associatedwith a front contact assembly in the plurality of front contactassemblies and each rear port in the plurality of rear ports isassociated with a rear contact assembly in the plurality of rear contactassemblies, wherein when a rear contact assembly is electrically coupledto a connector, the connector generates an event that is sent to themanaging entity, whereupon the managing entity remaps the portidentification for the plurality of front ports and the plurality ofrear ports.

Example 2 includes the system of Example 1, wherein the rear contactassembly includes a rear general purpose input/output (GPIO) pin and thefront contact assembly includes a front GPIO pin, where the rear GPIOpin produces a different signal from the front GPIO pin.

Example 3 includes the system of Example 2, wherein the front GPIO pinproduces a logically high voltage and the rear GPIO pin produceslogically low voltage.

Example 4 includes the system of any of Examples 1-3, wherein remappingthe port identification for the plurality of front ports and theplurality of rear ports comprises reversing the number order of theports.

Example 5 includes the system of any of Examples 1-4, wherein themanaging entity notifies a user that the port identification has beenremapped.

Example 6 includes the system of any of Examples 1-5, wherein themanaging entity manages a frame assembly containing the adapter block.

Example 7 includes the system of any of Examples 1-6, wherein theadapter block is at least one of the following: an LC/LC adapter; anSC/SC adapter; and an MPO/MPO adapter.

Example 8 includes the system of any of Examples 1-7, wherein the modulegenerates a module event for transmission to the managing entity whenthe module is installed within a chassis in a reversed position.

Example 9 includes the system of Example 8, wherein the managing entitynotifies a user that the module is installed in a reversed position uponthe reception of the module event.

Example 10 includes an optical distribution frame comprising: a framestructure defining a plurality of positions into which a plurality ofchassis can be inserted; and a frame controller unit attached to theframe structure, the frame structure comprising: a frame controller; andat least one chassis, wherein the at least one chassis includes at leastone module including at least one adapter block, wherein the adapterblock comprises: a plurality of front ports and a plurality of rearports configured to receive an optical connector; and a circuit boardmounted to the adapter block, wherein the circuit board comprises aplurality of front contact assemblies and a plurality of rear contactassemblies, wherein each front port in the plurality of front ports isassociated with a front contact assembly in the plurality of frontcontact assemblies and each rear port in the plurality of rear ports isassociated with a rear contact assembly in the plurality of rear contactassemblies, wherein when a rear contact assembly is electrically coupledto a connector, the connector generates an event that is sent to theframe controller; a switch communicatively coupled to the framecontroller; at least one cable attached to the switch and routed andattached to the optical distribution frame so that the at least onecable can be attached to the at least one chassis inserted into apredetermined one of the plurality of positions in the opticaldistribution frame; wherein the frame controller is configured tocommunicate port mapping information and the event to a managemententity that is communicatively coupled to the frame controller,whereupon the managing entity remaps the port identification for theplurality of front ports and the plurality of rear ports when the eventis received.

Example 11 includes the system of Example 10, wherein the rear contactassembly includes a rear general purpose input/output (GPIO) pin and thefront contact assembly includes a front GPIO pin, where the rear GPIOpin produces a different signal from the front GPIO pin.

Example 12 includes the system of Example 11, wherein the front GPIO pinproduces a logically high voltage and the rear GPIO pin produceslogically low voltage.

Example 13 includes the system of any of Examples 10-12, whereinremapping the port identification for the plurality of front ports andthe plurality of rear ports comprises reversing the number order of theports.

Example 14 includes the system of any of Examples 10-13, wherein themanaging entity notifies a user that the port identification has beenreassigned.

Example 15 includes the system of any of Examples 10-14, wherein themanagement entity associates location information with the plurality ofrear ports and the plurality of front ports.

Example 16 includes the system of any of Examples 10-15, wherein theadapter block is at least one of the following: an LC/LC adapter; anSC/SC adapter; and an MPO/MPO adapter.

Example 17 includes the system of any of Examples 10-16, wherein the atleast one module generates a module event for transmission to themanaging entity when the at least one module is installed within the atleast one chassis in a reversed position.

Example 18 includes the system of Example 17, wherein the managingentity notifies a user that the at least one module is installed in areversed position upon the reception of the module event.

Example 19 includes a method for detecting component rotation, themethod comprising: placing a module within a chassis; placing an adapterblock within the module; coupling a connector to a port in the adapterblock; determining whether the module generates a module event;determining whether the connector generates an adapter event; and whenthe connector generates the adapter event, remapping identification ofthe port.

Example 20 includes the method of Example 19, wherein the adapter blockcomprises: a plurality of front ports and a plurality of rear portsconfigured to receive optical connectors; and a circuit board mounted tothe adapter block, wherein the circuit board comprises a plurality offront contact assemblies and a plurality of rear contact assemblies,wherein each front port in the plurality of front ports is associatedwith a front contact assembly in the plurality of front contactassemblies and each rear port in the plurality of rear ports isassociated with a rear contact assembly in the plurality of rear contactassemblies, wherein when a rear contact assembly is electrically coupledto a connector, the connector generates adapter events for transmissionto a managing entity.

Example 21 includes the method of Example 20, wherein the rear contactassembly includes a rear general purpose input/output (GPIO) pin and thefront contact assembly includes front GPIO pin, where the rear GPIO pinproduces a different signal from the front GPIO pin.

Example 22 includes the method of Example 21, wherein the front GPIO pinproduces a logically high voltage and the rear GPIO pin produceslogically low voltage.

Example 23 includes the method of any of Examples 19-22, whereinremapping identification of the port comprises: transmitting the adapterevent to a managing entity; and reversing the order of the ports.

Example 24 includes the method of Example 23, wherein the managingentity notifies a user that the port identification has been reassigned.

Example 25 includes the method of any of Examples 19-24, whereindetermining whether the module generates a module event comprises:detecting when the module is installed in a reverse position; and whenthe module is installed in a reverse position, generating a module eventfor transmission to a managing entity.

Example 26 includes the method of Example 25, wherein the managingentity notifies a user that the module is installed in the reverseposition.

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications to the described embodiments maybe made without departing from the spirit and scope of the claimedinvention. Also, combinations of the individual features of theabove-described embodiments are considered within the scope of theinventions disclosed here.

What is claimed is:
 1. A system for detecting component rotation, thesystem comprising: a module; an adapter block installed in the module,the adapter block comprising a plurality of front ports and a pluralityof rear ports configured to receive an optical connector; a managingentity configured to control port identification for the plurality offront ports and the plurality of rear ports; and a circuit board mountedto the adapter block, wherein the circuit board comprises a plurality offront contact assemblies and a plurality of rear contact assemblies,wherein each front port in the plurality of front ports is associatedwith a front contact assembly in the plurality of front contactassemblies and each rear port in the plurality of rear ports isassociated with a rear contact assembly in the plurality of rear contactassemblies, wherein when a rear contact assembly is electrically coupledto a connector, the connector generates an event that is sent to themanaging entity, whereupon the managing entity remaps the portidentification for the plurality of front ports and the plurality ofrear ports based on an orientation of the adapter block.
 2. The systemof claim 1, wherein the rear contact assembly includes a rear generalpurpose input/output (GPIO) pin and the front contact assembly includesa front GPIO pin, where the rear GPIO pin produces a different signalfrom the front GPIO pin.
 3. The system of claim 2, wherein the frontGPIO pin produces a logically high voltage and the rear GPIO pinproduces logically low voltage.
 4. The system of claim 1, whereinremapping the port identification for the plurality of front ports andthe plurality of rear ports comprises reversing a number order of theports.
 5. The system of claim 1, wherein the managing entity notifies auser that the port identification has been remapped.
 6. The system ofclaim 1, wherein the managing entity manages a frame assembly containingthe adapter block.
 7. The system of claim 1, wherein the adapter blockis at least one of the following: an LC/LC adapter; an SC/SC adapter;and an MPO/MPO adapter.
 8. The system of claim 1, wherein the modulegenerates a module event for transmission to the managing entity whenthe module is installed within a chassis in a reversed position.
 9. Thesystem of claim 8, wherein the managing entity notifies a user that themodule is installed in a reversed position upon the reception of themodule event.
 10. An optical distribution frame comprising: a framestructure defining a plurality of positions into which a plurality ofchassis can be inserted; and a frame controller unit attached to theframe structure, the frame structure comprising: a frame controller; andat least one chassis, wherein the at least one chassis includes at leastone module including at least one adapter block, wherein the adapterblock comprises: a plurality of front ports and a plurality of rearports configured to receive an optical connector; and a circuit boardmounted to the adapter block, wherein the circuit board comprises aplurality of front contact assemblies and a plurality of rear contactassemblies, wherein each front port in the plurality of front ports isassociated with a front contact assembly in the plurality of frontcontact assemblies and each rear port in the plurality of rear ports isassociated with a rear contact assembly in the plurality of rear contactassemblies, wherein when a rear contact assembly is electrically coupledto a connector, the connector generates an event that is sent to amanagement entity, the management entity configured to control portidentification for the plurality of front ports and the plurality ofrear ports based on an orientation of the adapter block; a switchcommunicatively coupled to the frame controller; at least one cableattached to the switch and routed and attached to the opticaldistribution frame so that the at least one cable can be attached to theat least one chassis inserted into a predetermined one of the pluralityof positions in the optical distribution frame; wherein the framecontroller is configured to communicate port mapping information to themanagement entity that is communicatively coupled to the framecontroller; and wherein the managing entity remaps the portidentification for the plurality of front ports and the plurality ofrear ports when the event is received.
 11. The system of claim 10,wherein the rear contact assembly includes a rear general purposeinput/output (GPIO) pin and the front contact assembly includes a frontGPIO pin, where the rear GPIO pin produces a different signal from thefront GPIO pin.
 12. The system of claim 11, wherein the front GPIO pinproduces a logically high voltage and the rear GPIO pin produceslogically low voltage.
 13. The system of claim 10, wherein remapping theport identification for the plurality of front ports and the pluralityof rear ports comprises reversing a number order of the ports.
 14. Thesystem of claim 10, wherein the managing entity notifies a user that theport identification has been reassigned.
 15. The system of claim 10,wherein the management entity associates location information with theplurality of rear ports and the plurality of front ports.
 16. The systemof claim 10, wherein the adapter block is at least one of the following:an LC/LC adapter; an SC/SC adapter; and an MPO/MPO adapter.
 17. Thesystem of claim 10, wherein the at least one module generates a moduleevent for transmission to the managing entity when the at least onemodule is installed within the at least one chassis in a reversedposition.
 18. The system of claim 17, wherein the managing entitynotifies a user that the at least one module is installed in a reversedposition upon the reception of the module event.